home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Precision Software Appli…tions Silver Collection 1
/
Precision Software Applications Silver Collection Volume One (PSM) (1993).iso
/
demos
/
mag6demo.exe
/
M600D2.ZIP
/
MAG6.NEW
< prev
next >
Wrap
Text File
|
1992-06-09
|
26KB
|
587 lines
June, 1992
Welcome to Magnum BBS version 6.00D2 (2-node DEMO)
This document will guide you through installing Magnum BBS version 6.00D2
over your existing v5.02D2 version of Magnum.
==> If you're installing version 6.00D2 and this is your FIRST (only)
version of Magnum, then you may skip this document entirely. This
document is only for those upgrading from version 5.02D2.
If you've never installed any version of Magnum BBS, then skip this
document and proceed with the instructions in the user manual!
-------------------------------------------------------------------------
To install Magnum version 6.00D2 over your existing 5.02D2 version of
Magnum, follow these steps exactly:
0) DO NOT COPY ANY NEW FILES FROM 6.00D2 UNTIL INSTRUCTED TO DO SO!!!
STEPS 1 thru 4 require the use of your OLD (current) programs!
1) SHUT DOWN your system!
A) Issue the "* ENDNOW" command from the MBBS.EXE command prompt.
B) At the OS/2 Command Prompt, Issue the following command:
STOPRJE *
Wait for the STOPRJE program to complete (30 seconds).
2) BACK UP your system! As a minimum, back up the following directories:
PROGRAM DIRectory
SESSION DIRectory (All *.DAT and *.KEY files)
EXTERNAL DIRectory
RJE DIRectory
W A R N I N G >>> IF YOU DO NOT BACK UP THESE DIRECTORIES, WE CAN NOT
>>> HELP YOU IN CASE OF ANY PROBLEMS!!!!
3) Run the Following Commands for each existing copy of MBBSINIT.x :
MAKEMBBS -1 >STARTUP.1
MAKEMBBS -2 >STARTUP.2
4A) -> Insert the following text line (OPTIONAL) in each of your STARTUP.x
files:
CONFIRM_NEWRESP: N
The CONFIRM_NEWRESP: keyword accepts a Y (yes) or N (no) response. The
default is N. If you supply N (no), Magnum will not confirm new user
logon responses with the "Is this correct (Y/N) => " prompt when new
users respond to the prompts of address, city, state, zip, country,
telephone numbers, etc. Instead, the new user will have a chance to
update their responses at the end of all of the new user logon
questions. If you supply a Y (yes) as the parameter, Magnum will
operate as before. We recommend the default of N. This keyword exists
only for compatibility with previous Magnum versions for the sake of
those callers with automated scripts being used with their
telecommunications programs.
4B) For EACH of your STARTUP.x file(s), edit them as follows with your
favorite text editor:
-> Insert the following text line (modify to your liking) in each of your
STARTUP.x files:
FILEMENU_UTILS: E,5,[E]asy Utils (Mark,UnMark,etc)
This should go along with the rest of the FILEMENU_xxxxx: keywords.
If you allow your users access to this function, the file menu will
present the user with the same utility they would ordinarily get by
choosing [U]tils in response to the -More- prompt during file
listings. This functionality has been added for convenience and for
those who got frustrated because they couldn't mark any files towards
the end of a file list due to the -More- prompt not appearing at the
end of a file list.
-> Insert the following text line (OPTIONAL) in each of your STARTUP.x
files:
MILC_CHAR: @
The parm (character) you supply for this keyword will override the
default MILC command character of '@'.
NOTE: characters with decimal values of 0 to 32 (hex 0 to hex 20)
will not be accepted. Alphanumeric characters (A-Z, a-z, 0-9)
and punctuation characters will NOT be accepted: !,.?"':;()
CAUTION: If using someone else's MILC command file, chances are very
high that they're using the @ character; you must be sure
to change this to the MILC command character you define for
your system. If you'll be overriding the MILC command
character, use extreme caution in selecting a new character!
Avoid the use of characters which may appear within a normal
message (ie: %$#*[]{}\/<>+-&).
Try to pick a not-so-common character such ~ or ^
-> Insert the following text line (OPTIONAL) in each of your STARTUP.x
files:
SHOW_CALLERNUM: Y
If you supply Y to this keyword, Magnum will function as usual. If
you supply N to this keyword, Magnum will suppress the "You are the
nth caller on node x" message when a user logs on.
-> Insert the following text line (OPTIONAL) in each of your STARTUP.x
files:
SHOW_DLS: Y
If you supply Y to this keyword, Magnum will function as usual. If
you supply N to this keyword, Magnum will suppress the information
on the number of Downloads on each file during any file listings.
5) Almost There....
A) Once you've made the changes to ALL of your STARTUP.x files in
step 4 above, copy 2 files from the distribution diskette in
drive A with the following commands (you should be in your
PROGRAM DIRectory at this time):
COPY A:\MAGNUM\PGM_DIR\MAKEMBBS.EXE
COPY A:\MAGNUM\PGM_DIR\MUPDATE.EXE
B) "Compile" your new STARTUP.x files with the new MAKEMBBS.EXE
program with the following command:
MAKEMBBS
C) Once step B above has been successfully run for all of your STARTUP.x
files, run the following program:
MUPDATE
D) After MUPDATE.EXE completes from step 5C above, MUPDTx.CMD file(s)
will be created. If the directory paths for your PROGRAM, RJE, and
EXTERNAL directories are identical for each of your nodes, then
run any of the MUPDTx.CMD file(s) created from step 5C above since
they will all be identical. If any of your nodes has unique
(different) PROGRAM, RJE, or EXTERNAL directory paths from your
other node(s), then run each corresponding MUPDTx.CMD for each
node having a different directory path.
E) Change to your SESSION DIRectory (make it the current directory)
and run the program:
SPLITKEY.EXE
F) Making sure you're in your PROGRAM DIRectory, run the following
.MEX program to initialize the new fields in your USER database:
MBBSEXEC.EXE VER6_00U
- Making sure you're in your PROGRAM DIRectory, run the following
.MEX program to initialize the new fields in your MSG database:
MBBSEXEC.EXE VER6_00M
F) Change back to your PROGRAM DIRectory (make it the current
directory).
G) Repeat step 3) above at your leisure just to have new copies
of your STARTUP.x file(s) around.
6) ReStart your BBS:
MBBS.EXE
Some of you may have a .CMD file to start your BBS with. If so, then
start your .CMD file now!
7) Read the remainder of this document for a list of Changes,
Enhancements, etc.
As always, you'll find more power with this release than any of the
previous releases!
-------------------------------------------------------------------------
*** Congratulations! You've just installed Magnum BBS ver 6.00Cxx.
Your feedback is very important to us! If you run into any problems
or have any comments or suggestions, do not hesitate to tell us about
them! Your feedback helps shape the production versions of Magnum BBS.
Thank you for using Magnum BBS for OS/2.
===========================================================================
******************************************
* Changes/Enhancements for version 6.00C *
******************************************
/============================\
< MAGNUM BBS - VERSION 6.00C >
\============================/
(C)Copyright 1989, 1992 Gilmore Systems - All Rights Reserved
/======\
< NOTES: >
\======/
- If you have a copy of CMD.EXE in your EXTERNAL DIRectory, then remove
it! As long as CMD.EXE is in your PATH statement (prior to starting
MBBS.EXE), Magnum will find it! Having a separate copy of CMD.EXE
in your EXTERNAL DIRectory is not only a waste of space, but a potential
hazard when upgrading to a new version of OS/2 or applying a CSD unless
you remember to replace the CMD.EXE in your EXTERNAL DIRectory as well!
It's much simpler to just remove CMD.EXE from your EXTERNAL DIRectory!
- With this version especially, you should have the pathnames of your
EXTERNAL and PROGRAM DIRectories in your OS/2 PATH statement PRIOR to
starting Magnum. You can do this with the SET PATH= statement in your
CONFIG.SYS file.
/================================\
< VER6_00U.MEX (new .MEX program): >
\================================/
- This is the .MEX file needed to initialize the new fields in the USER
database prior to starting your version 6.00 system. This .MEX program
is only used if you're installing over the 5.02D2 version of Magnum.
/================================\
< VER6_00M.MEX (new .MEX program): >
\================================/
- This is the .MEX file needed to initialize the new fields in the MSG
database prior to starting your version 6.00 system. This .MEX program
is only used if you're installing over the 5.02D2 version of Magnum.
/===========================\
< SPLITKEY.EXE (new program): >
\===========================/
- This is a new program which prepares the new USER.KEY and USER_?.KEY
files for this release of Magnum.
- After initially running this program as per the installation instructions,
save this program for later use. In the event your *.KEY file(s) become
damaged (or lost) for any reason, running this program will re-create
all of your *.KEY files from the USER.DAT file. Before using this program
for re-creation, however, you must back up your *.KEY files!!
- The SPLITKEY.EXE program will reject all LastName's not starting with one
of the following characters:
- alphanumeric (A-Z, a-z, 0-9)
- underscore ( _ ) character
- dollar ( $ ) character
If the last name of any record does not start with one of these characters,
the record for this file will not be rebuilt into a key file, but the last
name will change to ERRORxxxxx (where xxxxx is the ID of that user account).
- Note: If you change someone's LAST NAME, whether with MBBSEXEC.EXE or via
the Sysop menu, you'll need to rerun SPLITKEY.EXE, however, you can
save time by running it with the first initial of the user's last
name (before & after). For example, if you change one of your user's
last name from DOE to SMITH, you would run SPLITKEY twice as follows:
SPLITKEY D
SPLITKEY S
This causes the SPLITKEY program to rebuild USER_D.KEY and USER_S.KEY
files.
/=============\
< MBBSEXEC.EXE: >
\=============/
- When processing the FILE database, the keyword @DATELAST was being
confused with the keyword @DATE instead. This has been corrected.
- Corrected possible flaw in handling @SENDNULLS and @FILELIST_PREF keywords
in USER database.
- The appearance of the }ELSE{ statement in .MEX programs seems to throw
off the readability of these source files. Starting with this version,
you can use the word ELSE instead of }ELSE{. When MBBSEXEC.EXE reads your
source .MEX program, it will automatically convert these ELSE statements
to the }ELSE{ statements it expects. Example:
The 'old' style:
IF(@DELETED == TRUE) {
LOG("Deleted Record")
}ELSE{
LOG("Active Record")
}
can still be used, however the new format is easier to read:
IF(@DELETED == TRUE) {
LOG("Deleted Record")
ELSE
LOG("Active Record")
}
You still need the { after the IF() statement, and you need the closing
} on a line by itself. Note that you can have as many statements as you
want between any given IF/ELSE statment, and as many statements as you
want between and given ELSE and close } character. As always, indentation
is only important for readability and has no bearing on how MBBSEXEC.EXE
interprets your code. Your code can still be as nested as you wish:
IF(expression1) {
.
.
ELSE
IF(expression2) {
.
.
ELSE
IF(expression3) {
IF(expression4) {
.
.
}
}
}
}
/=========\
< MBBS.EXE: >
\=========/
- The number of stored ACE commands has been increased to 300 (formerly 100).
- New "Command => " commands:
x ONHOOK ................. Sends ONHOOK sequence to modem on node x
x OFFHOOK ................. Sends OFFHOOK sequence to modem on node x
- New "Command => " Command:
* LOGOCOLOR x
where 'x' is a number ranging from 1 to 15. The color value of this number
is the same as the values of the * COLOR statement. This command changes
the color of the logo appearing at the top of the screen. The purpose of
this command is because the default color does not show up on monochrome
screens.
- New "Command => " Command:
* FRAMECOLOR x
where 'x' is a number ranging from 1 to 15. The color value of this number
is the same as the values of the * COLOR statement. This command changes
the color of the frames appearing around the node displays. The purpose of
this command is because the default color does not show up on monochrome
screens.
- The Serial Number of your MBBS.EXE program is now displayed on the screen
to the right of the "Magnum BBS (r)" trademark. Both the trademark and
serial number are displayed in white.
- The indication of the node numbers which currently have someone online
(located on the right side of the screen on the same display line as
the date & time) has been changed to realtime. MBBS no longer waits to
update this display at the old 60-second interval.
/=============\
< MAKEMBBS.EXE: >
\=============/
- New Keyword FILEMENU_UTILS: now added. This should go along with the
rest of the FILEMENU_xxxxx: keywords. If you allow your users access
to this function, the file menu will present the user with the same
utility they would ordinarily get by choosing [U]tils in response to
the -More- prompt during file listings. This functionality has been added
for convenience and for those who got frustrated because they couldn't
mark any files towards the end of a file list due to the -More- prompt
not appearing at the end of a file list.
- New optional Keyword MILC_CHAR: now added. The parm you supply for this
keyword will override the default MILC command character of '@'.
NOTE: characters with decimal values of 0 to 32 (hex 0 to hex 20) will
not be accepted. Alphanumeric characters (A-Z, a-z, 0-9) and
punctuation characters will NOT be accepted: !,.?"':;()
CAUTION: If using someone else's MILC command file, chances are very
high that they're using the @ character; you must be sure to
change this to the MILC command character you define for your
system.
If you'll be overriding the MILC command character, use extreme
caution in selecting a new character! Avoid the use of characters
which may appear within a normal message (ie: %$#*[]{}\/<>+-&).
Try to pick a not-so-common character such as the ~ or ^ character.
- New optional Keyword SHOW_CALLERNUM: now added. If you supply Y to this
keyword, Magnum will function as usual. If you supply N to this keyword,
Magnum will suppress the "You are the nth caller on node x" message.
- New optional Keyword SHOW_DLS: now added. If you supply Y to this keyword,
Magnum will function as usual. If you supply N to this keyword, Magnum will
suppress the information on the number of Downloads on each file during
any file listings.
- New (optional) keyword can be added to your STARTUP.x file(s):
CONFIRM_NEWRESP: N
The CONFIRM_NEWRESP: keyword accepts a Y (yes) or N (no) response. The
default is N. If you supply N (no), Magnum will not confirm new user
logon responses with the "Is this correct (Y/N) => " prompt when new users
respond to the prompts of address, city, state, zip, country, telephone
numbers, etc. Instead, the new user will have a chance to update their
responses at the end of all of the new user logon questions. If you supply
a Y (yes) as the parameter, Magnum will operate as before. We recommend
the default of N. This keyword exists only for compatibility with previous
Magnum versions for the sake of those callers with automated scripts being
used with their telecommunications programs.
/=============\
< MSESSION.EXE: >
\=============/
- The "[N]ew Files" function within the files menu did not accept a valid
02/29 (or 29.02) date. This has been corrected.
- When uploading a file, Magnum checks the BADUPLD.LST file (if it exists)
to determine if the Sysop disallows uploads matching certain criteria in
the upload filename. A bug in this checking presented itself such that
(by way of example) if PMGIF.* were in the BADUPLD.LST file, then Magnum
would mistake this to be PMGIF*.* instead of PMGIF.* which was incorrect.
This has been fixed.
- During NonStop File Listing (ie: User supplies N to the -More- prompt
to signify nonstop scrolling) Magnum would ocassionally produce the
-More- prompt when displaying a matching FDIR*.BBS or FDIR*.SCR file.
This has been corrected.
- If logging on locally (via the Sysop console), the screen would not
clear when you saw the "Good Morning" (or afternoon or evening) message
if your color settings were set to N (off). This has been corrected.
- We've received several complaints that the file COMPRESS.LST was not
functioning correctly. This was due to sysops who've inserted TAB
characters into the file. To correct this problem, Magnum now strips
out (ignores) these TAB characters.
- The [U]ser Search function from main menu now has significant speed
improvements when searching for someone by last name.
- During File Listings, if there's no Expiration date for a file, the
"EXPIRES: No Expire." text is no longer displayed.
- Message receipts are now generated in the same conference area as the
message for which the receipt was requested.
Other system-generated messages will still be placed in the PRIVMSG_AREA
as designated in your STARTUP.n file(s).
- The caller number (ie: nth caller for node x) is now logged to the
ACTIVITY.n file(s).
- The prompt "- More - (C)ontinue, [S]top, [N]onstop, [U]tils => " during
a Files listing (the [U]tils portion) has been enhanced such that the
user can review/modify the list of files s/he has marked.
- New functionality has been added to the file menu. The same utilities
available at the "- More - (C)ontinue, [S]top, [N]onstop, [U]tils => "
prompt (the [U]tils portion) during a file listing is now available as
its own menu selection from the file menu. See FILEMENU_UTILS: under the
first paragraph of the heading MAKEMBBS.EXE above.
- The [E]nvironment section of the main menu (where users can change
their system/personal paramters) is now configurable by the Sysop as
to which parameters may/may not be changed. If you wish all parameters
to be changeable (as before), then do nothing! Otherwise, create the
file NOCHANGE.LST in your SESSION DIRectory. This file is an ASCII
text file which contains the numbers (1 thru 24 in this release)
of which parameters you do NOT want your users to be able to change!
For example, if you don't want users to be able to change System
compression type (choice 1) or their birthdate (choice 11), then the
file NOCHANGE.LST would contain the two menu numbers as follows:
1
11
The format of the file is one menu number per text line.
- The display of the PREDOWN.BBS file (prior to downloading) has been
changed such that it will ALWAYS display regardless of whether the
user has a default protocol selected or not. It has been changed so
that it will ALWAYS display even if command-stack-chaining has been
used. If you do not wish this file to display when a default protocol
has been chosen, you may test to see if one has been chosen with MILC
commands and then act accordingly. The purpose of this is to ensure
those sysops who rely on MILC commands within this file (to invoke
an external program, for example) to always be able to execute these
commands under any circumstances.
- New MILC Commands added:
@?x - File Existence. This command tests for the existence of a file.
The filename ([d:][path]filename[.ext]) to test is in @Zx. The
result is placed in @N0 (1=exists, 0=does not exist).
Example:
@Z5="d:\magnum\testfile.ext";
@?5
@b1(n0=1); The file does NOT exist!
@c16
@p1 The file DOES exist!
NOTE: Like the @$x, @&x and @!x commands, this command is only
available to the Sysop or the System. Users other than
the Sysop do not have access to this command!
@E10 - Disable output. Suspend all output to modem or screen. All output
sent following this command will be discarded (ignored) until the
@E11 command is issued.
@E11 - Enable output. Negates @E10, resumes output.
@T"string" --\
or > This command writes to the ACTIVITY file. There are two
@Tx ---------/ ways of writing to the ACTIVITY file (via examples):
The following example writes the text appearing within
the double-quotes to the ACTIVITY file:
@T"This is a sample text line"
The following example writes the contents of variable
@Z5 to the ACTIVITY file:
@T5
- The new user logon procedure has been modified. When a new user logs on for
the first time, the first character of their last name must be one of:
- alphanumeric (A-Z, a-z, 0-9)
- underscore ( _ ) character
- dollar ( $ ) character
The SPLITKEY.EXE program (above) will also be consistent with these rules.
- When a new user logs on for the first time, if your system is configured
to ask for areas of personal interest, the old text used to read:
Magnum OS/2 BBS software stores your personal areas of interest.....
It will now read:
"Your BBS Name" stores your personal interest areas....
where "Your BBS Name" will be replaced with the name of your BBS.
- New MILC commands added:
@E12 - Disable Timer. This command comes in handy when someone is about
to run out of time on your system, and you want them to have more
time. For example, suppose you run a subscription service or offer
an 'online order' menu in which users can place credit card orders.
We've seen users get logged off by Magnum because they ran out of
time, yet they were in the middle of trying to place on online
order! When you use the new @E12 command, this will no longer
happen. The timer is temporarily suspended with this command,
until you issue an @E13 command to reactivate the timer.
NOTE: If you forget to negate this command with the @E13 command,
the timer will not reactivate! Therefore, we've built in
a safety measure. If you use this command, Magnum will
automatically issue an @E13 command internally after a
period of 5 minutes.
@E13 - Enable Timer. Negates @E12.
- Just to get things straight between upgrades, you can verify which version
of MSESSION.EXE you have by entering MSESSION.EXE /V (You can also do this
with MBBS.EXE).
=============================================================================
NOTE:
The above compilation has been a listing of changes/enhancements to the
DEMO version and does NOT include a summary of the changes/enhancments
we've made to the commercial (ship-level) version. Although all of the
above changes/enhancements exist in the commercial version, there have
been other significant enhancements in the commercial version such as
Magnum-to-Magnum remote mail (built in), file and message groups for
those using the extended file and/or messagebase modules, etc.
=============================================================================